The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 5, 2026 1:00am

PR Summary

Low Risk
Low risk: adds optional query parameters and UI inputs to servicenow_read_record without changing existing defaults, but could affect pagination/display behavior if misused.

Overview
Adds two new optional inputs to servicenow_read_record: offset (mapped to sysparm_offset) for pagination and displayValue (mapped to sysparm_display_value) to control whether reference fields return sys_ids, display values, or both.

Updates the ServiceNow block UI/config to expose these parameters (including type coercion for limit/offset) and updates docs/types so the new options are reflected end-to-end.

^{Written by Cursor Bugbot for commit 18982b8. Configure here.}

Greptile Summary

This PR adds two new optional parameters to the ServiceNow Read Records operation: offset (sysparm_offset) for pagination support and displayValue (sysparm_display_value) to return human-readable display values for reference fields instead of raw sys_ids.

• offset is exposed as a short-input in advanced mode and correctly coerced from string to number in the block params transform; the URL builder uses an explicit !== undefined && !== null guard that properly handles offset=0 (first-page reset).
• displayValue is exposed as a dropdown correctly defaulting to empty string ("Default (not set)"), with options for 'false', 'true', and 'all'; the URL builder uses a falsy check that correctly suppresses the empty-string default.
• All four changed files are consistent with each other and follow existing patterns.
• One remaining issue: empty strings in the offset field are not caught by the URL builder guard. A user clearing the offset field in the UI could result in sysparm_offset= being appended with no value, potentially causing a 400 error from ServiceNow.
• Tests were not added/updated for the new parameters as noted in the checklist.

Confidence Score: 3/5

• This PR introduces a latent bug where empty-string offset values can be sent to the ServiceNow API with no value, risking 400 errors.
• The feature additions are well-scoped and the offset=0 correctness issue has been fixed. However, a new issue remains: the empty-string case is not handled by the URL builder guard, allowing invalid query parameters to be sent. This is a concrete bug that occurs when users clear the offset field, though it's not immediately apparent and would manifest as an API error.
• apps/sim/tools/servicenow/read_record.ts — the offset guard must exclude empty strings or the block transform must coerce empty strings to undefined.

_{Last reviewed commit: c66926e}

@greptile

@cursor review

@greptile